Rebased onto current main after #346 and force-pushed e1c7e1d34.

Verification after rebase:

• yarn install --frozen-lockfile ✅
• yarn build ✅
• yarn tsc-check-noimplicitany ✅
• yarn tsc-check ✅
• npx prettier --check package.json ✅
• yarn audit --level high ✅ no high/critical advisories in JSON audit stream

GitHub reports the branch as mergeable now; current blocked state appears to be review/check gating rather than conflicts.

What kind of testing has been done to ensure no regression?

iOS and Android smoke testing of maps screens, send, receive, settings, chat, camera.

Ledger test results for the medici ^6 → ^7 bump

Ran the ledger tests against this branch after a clean yarn install --frozen-lockfile.

✅ Ledger unit tests — pass

test/flash/unit/domain/ledger/imbalance-calculator.spec.ts   ✓ (7)
test/flash/unit/domain/ledger/activity-checker.spec.ts       ✓ (6)
test/flash/unit/domain/ledger/fee-reimbursement.spec.ts      ✓ (12)
test/flash/unit/domain/ledger/index.spec.ts                  ✓ (1)
Test Suites: 4 passed, 4 total   Tests: 26 passed, 26 total

Good signal that the medici-7 surface the domain layer uses (MediciEntry/Entry types, LedgerService translation, fee/imbalance logic) is compatible.

⚠️ Ledger integration tests — not yet validated (infra, not a medici failure)

The specs that actually write medici Book/Entry records are the real test of this bump:

• test/flash/integration/services/ledger/onchain-send.spec.ts
• test/flash/integration/services/ledger/cashout.spec.ts

Two blockers to running them:

1. They're excluded from the suite. test/flash/integration/jest.config.js sets testPathIgnorePatterns: [".../integration/services/*", ".../integration/wallet/*"], so yarn test:integration never runs them. (cashout.spec.ts also has its Ibex mocks commented out.)
2. They need the full harness. I stood up Mongo (replica set, for medici v7 transactions) + Redis and injected the required --configPath, but beforeAll hung with 0 users written — createMandatoryUsers()/createUser() provision Kratos identities (Kratos + Postgres), which weren't running. That's the likely reason these live under the ignored services/* path.

Recommendation before merge

A medici major bump touches the live double-entry ledger engine, so unit-green is necessary but not sufficient. Please validate the two services/ledger specs end-to-end in the project's integration docker stack (Mongo + Redis + Kratos + Postgres) with the ignore pattern lifted, so we confirm medici 7 actually writes balanced transactions on the real paths (on-chain send, cashout). Build/typecheck/audit + ledger unit tests are otherwise green.